docs(readme): replace stale v0.7.0 with the v0.x line - #645

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Claude finished @kyle-sexton's task in 33s —— View job

/review:code-review

• Gather context (diff, README surrounding paragraph, repo-wide search for stale references)
• Apply skip gate
• Post result

Skip gate hit: trivial documentation change with no meaningful review surface (criterion 3).

The diff replaces a stale v0.7.0 literal with v0.x in the Versioning section's one sentence that referenced it:

-4][semver]). This repository is `v0.7.0` at the time of writing: a release may
+4][semver]). This repository is on the `v0.x` line: a release may

Checked:

• Surrounding paragraph (README.md lines 96–104) still reads coherently with the new wording.
• No other v0.7.0 reference remains anywhere in the repo, so the fix is complete and consistent.
• No security, observability, atomicity, or architecture concerns apply to a one-line doc wording change (REVIEW.md code-review-lane checks).

No findings to report.

Claude finished @kyle-sexton's task in 14s —— View job

Security review

• Gather context (PR diff, change scope)
• Run /review:security-review skip-gate check
• Post results

Skip gate: no security-relevant surface.

This PR changes one line of prose in README.md (v0.7.0 → v0.x), a documentation-only version-reference update. It touches no code, no GitHub Actions workflow, no permissions/config, and no instruction/guardrail file (CLAUDE.md, AGENTS.md, rules files, hooks), so the instruction-surface-deletion lens doesn't apply either. No injection surfaces, auth/access-control logic, or secret handling are involved.

No security issues found. Nothing to report.